Expand Chapter 10: semantic logging - #23

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Code Review

PR #23: Expand Chapter 10 — Semantic Logging (JA)

Overview

Replaces the 63-line Japanese stub with a full ~160-line chapter covering the Been carrier, auto-recorded metamorphosis logs, event context classes, the produced JSON structure, and a bridge to Chapter 13 (LDD). The category is promoted from Draft to Manual.

Issues

1. English version not updated (significant)

The Japanese page is promoted to category: Manual (and will now appear in the JA sidebar), but en/10-semantic-logging.md still has category: Draft with the old stub content. This creates an asymmetry:

• JA sidebar: shows Chapter 10
• EN sidebar: Chapter 10 is absent

CLAUDE.md also notes these pages are "intentionally hidden from the sidebar" — if the intent is to graduate JA to visible, the EN version should be updated in the same PR (or the PR description should explain the deliberate phasing).

2. Sidebar visibility is a side-effect of the category change

The mechanism hiding these pages from the sidebar is category: Draft (not sidebar: false as CLAUDE.md implies). Changing to category: Manual makes the chapter visible in the sidebar. This is likely intentional, but worth noting explicitly — the PR summary doesn't mention the sidebar change.

Positive aspects

• Content structure is excellent. The open/events/close framing maps cleanly to the JSON output example, making the concept immediately tangible.
• Code examples are idiomatic and consistent with Be Framework conventions seen elsewhere in the manual.
• Links are valid. ./13-vision-ldd.html and ./11-reference-resources.html both have matching permalink values in their frontmatter.
• The $been exclusion note ("ログが自分自身を含めば無限再帰になる") is a helpful implementation detail.
• The LDD bridge at the end is well-placed — it earns the forward reference rather than just dropping a link.

Minor

• The trailing emoji (➡️) in the last line is the only emoji in the documentation. Consistent with not using emojis unless requested, consider replacing with plain text: "フレームワークの全体像はリファレンスへ。"

Summary

The content itself is high quality and ready. The main thing to address before merging is the EN/JA parity gap — either update en/10-semantic-logging.md to match or explicitly scope this PR as JA-only with a follow-up issue for EN.